home *** CD-ROM | disk | FTP | other *** search
- Path: camelot.dsccc.com!not-for-mail
- From: kcline@sun152.spd.dsccc.com (Kevin Cline)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++
- Subject: Re: C/C++ knocks the crap out of Ada
- Date: 11 Mar 1996 10:22:53 -0600
- Organization: DSC Communications Corporation Switch Products Division
- Message-ID: <4i1k0t$9us@sun152.spd.dsccc.com>
- References: <JSA.96Feb16135027@organon.com> <4hhred$1rn@sun152.spd.dsccc.com> <adaworksDntn85.50y@netcom.com> <Dnxw7F.J04@thomsoft.com>
- NNTP-Posting-Host: sun152.spd.dsccc.com
-
- In article <Dnxw7F.J04@thomsoft.com>,
- Pascal Martin @lone <pmartin@alsys.com> wrote:
- >
- >>: to be hard for Ada to keep up. To use Ada in my work today, I would
- >>: require an API to CORBA, Tcl/Tk, and the Solaris real-time facilities
- >>: (itimers, etc.) and a runtime that efficiently mapped Ada tasks to
- >>: Solaris threads.
- >
- >I am myself using Tcl from Ada. It took less than one afternoon for getting a
- >minimal set of interfaces between Ada and Tcl to work, including callbacks.
- >This was with our own compilers on Sparc and Hp700 (on engineer here has
- >recently made a Windows95/WindowsNT port). I know there is a free Tcl binding
- >for both Vads and GNAT.
- >
-
- Yes, but is it the same binding? Is your minimal set of interfaces portable
- to GNAT without source code changes?
-
- >The Solaris threads are supported in our ObjectAda product. This is significantly
- >slower than our own previous 'user-mode' tasking, because of the Solaris
- >overhead. So much for the 'efficiently mapped': the most significant overhead
- >is *not* the Ada runtime.
-
- Of course 'user mode tasking' is cheaper than Solaris bound threads,
- but for most of the useful applications of threads on UNIX that I am
- familiar with, 'user mode tasking' is useless; it does not allow
- multiple tasks to proceed in parallel on different processors of a
- multi-processor system, and it does not allow one task to block in
- a UNIX I/O wait while other tasks proceed. Don't bother pointing
- out that standard ADA I/O does not cause all tasks to block;
- standard ADA I/O is so extremely limited that is is nearly useless
- for serious UNIX applications.
-
- --
- Kevin Cline
-